Method and apparatus for managing packet data network connectivity

ABSTRACT

Methods and apparatuses are provided for managing packet data network (PDN) connectivity for a device. A device may receive one or more parameters specifying whether PDN connectivity to a local gateway is allowed for the device at one or more access points. The one or more parameters can be specific for the device and/or for one or more access point names. The device can determine whether to initiate a PDN connection to the local gateway from at least one of the one or more access points based at least in part on the one or more parameters

CLAIM OF PRIORITY UNDER 35 U.S.C. § 119

The present application for patent is a Continuation application ofapplication Ser. No. 15/201,289 entitled “METHOD AND APPARATUS FORMANAGING PACKET DATA NETWORK CONNECTIVITY” filed Jul. 1, 2016, andassigned to the assignee hereof and hereby expressly incorporated byreference herein, which is a Divisional application of application Ser.No. 13/161,416, now U.S. Pat. No. 9,386,607, entitled “METHOD ANDAPPARATUS FOR MANAGING PACKET DATA NETWORK CONNECTIVITY” filed Jun. 15,2011, and assigned to the assignee hereof and hereby expresslyincorporated by reference herein, which claims priority to ProvisionalApplication No. 61/355,918 entitled “METHOD AND APPARATUS FOR ENFORCINGNETWORK SELECTION IN A ROAMING NETWORK” filed Jun. 17, 2010, andassigned to the assignee hereof and hereby expressly incorporated byreference herein, as well as Provisional Application No. 61/435,389entitled “MANAGEMENT OF LOCAL INTERNET PROTOCOL ACCESS USING APROVISIONED MEMORY IN A MOBILE ENTITY” filed Jan. 24, 2011, and assignedto the assignee hereof and hereby expressly incorporated by referenceherein.

BACKGROUND Field

The following description relates generally to wireless networkcommunications, and more particularly to managing packet data networkconnectivity.

Background

Wireless communication systems are widely deployed to provide varioustypes of communication content such as, for example, voice, data, and soon. Typical wireless communication systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing available system resources (e.g., bandwidth, transmit power, . .. ). Examples of such multiple-access systems may include code divisionmultiple access (CDMA) systems, time division multiple access (TDMA)systems, frequency division multiple access (FDMA) systems, orthogonalfrequency division multiple access (OFDMA) systems, and the like.Additionally, the systems can conform to specifications such as thirdgeneration partnership project (3GPP), 3GPP long term evolution (LTE),ultra mobile broadband (UMB), evolution data optimized (EV-DO), etc.

Generally, wireless multiple-access communication systems maysimultaneously support communication for multiple mobile devices. Eachmobile device may communicate with one or more base stations viatransmissions on forward and reverse links. The forward link (ordownlink) refers to the communication link from base stations to mobiledevices, and the reverse link (or uplink) refers to the communicationlink from mobile devices to base stations. Further, communicationsbetween mobile devices and base stations may be established viasingle-input single-output (SISO) systems, multiple-input single-output(MISO) systems, multiple-input multiple-output (MIMO) systems, and soforth. In addition, mobile devices can communicate with other mobiledevices (and/or base stations with other base stations) in peer-to-peerwireless network configurations.

To supplement conventional base stations, additional base stations canbe deployed to provide more robust wireless coverage to mobile devices.For example, wireless relay stations and low power base stations (e.g.,which can be commonly referred to as Home NodeBs or Home eNBs,collectively referred to as H(e)NB, femto access points, femtocells,picocells, microcells, etc.) can be deployed for incremental capacitygrowth, richer user experience, in-building or other specific geographiccoverage, and/or the like. In some configurations, such low power basestations are connected to the Internet and the mobile operator's networkvia broadband connection (e.g., digital subscriber line (DSL) router,cable or other modem, etc.). Some H(e)NBs provide closed subscribergroup (CSG) access that restricts access to certain devices or relatedusers that are members of the CSG. A home subscriber server (HSS), homelocation register (HLR), or one or more other nodes of a device's homenetwork can store CSG subscription information for the device (e.g., inaddition to general subscription information for the device), which caninclude one or more lists of CSGs of which the device is a member or canotherwise access.

In addition, by virtue of the broadband connection utilized by H(e)NBs,H(e)NBs can additionally acquire access to services or access toresources over a local network. In an example, where an H(e)NB utilizes(or provides) a gateway or router that can allow other devices to accessthe Internet or another packet data network (PDN), the devices and theH(e)NB can participate in a local PDN that is served by the gateway orrouter. In this example, the gateway or router can provide services oraccess to resources over the local PDN, such as storage devices,printers or other output devices, etc. The H(e)NB, in some examples, canprovide local internet protocol (IP) access (LIPA) to one or more mobiledevices communicating with the H(e)NB over a mobile network interfacesuch that the one or more mobile devices can access local resources onthe PDN as well via the H(e)NB (e.g., and/or devices on the localnetwork can access resources of the one or more mobile devices). Inanother example, an H(e)NB can implement selected IP traffic offload(SIPTO) for filtering traffic related to one or more devices over theInternet using the router in the PDN without forwarding the trafficthrough the mobile network.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In accordance with one or more embodiments and corresponding disclosurethereof, various aspects are described in connection with managingpacket data network (PDN) connectivity, such as local internet protocol(IP) access (LIPA), selected IP traffic offload (SIPTO), etc., for oneor more devices. For example, one or more parameters related to PDNconnectivity can be provided to a device for determining whether a PDNconnection is allowed with one or more access points with which thedevice is communicating. For example, the one or more parameters canspecify a list of access points with an indication of whether PDNconnectivity (e.g., in the form of LIPA, SIPTO, etc.) to a gateway isallowed for the device, a list of access points for which certain PDNconnectivity is allowed, a list of access point names (APN) related toone or more access points—or a grouping of access points, such as aclosed subscriber group (CSG), public land mobile network (PLMN),etc.—and indications of whether PDN connectivity is allowed for thedevice, a list of APNs for which certain PDN connectivity is allowed atone or more access points, and/or the like.

In addition, for example, the parameters can be specified in devicesubscription information, CSG information related to the device, and/orthe like. In any case, the device can determine whether to request orinitiate a PDN connection from an access point based at least in part onthe one or more parameters. This can mitigate unnecessary signalingwhere a device may otherwise request a PDN connection via an accesspoint with which PDN connectivity is not allowed.

According to an example, a method for utilizing PDN connectivity in awireless network is provided. The method includes receiving one or moreparameters specifying whether PDN connectivity to a local gateway isallowed at one or more access points and receiving a request toestablish a PDN connection to the local gateway while connected to atleast one of the one or more access points. The method further includesdetermining whether to initiate the PDN connection to the local gatewayusing the at least one of the one or more access points based at leastin part on the one or more parameters.

In another aspect, an apparatus for utilizing PDN connectivity in awireless network provided. The apparatus includes at least one processorconfigured to obtain one or more parameters specifying whether PDNconnectivity to a local gateway is allowed at one or more access pointsand receive a request to establish a PDN connection with the localgateway while connected to at least one of the one or more accesspoints. The at least one processor can be further configured todetermine whether to initiate the PDN connection to the local gatewayusing the at least one of the one or more access points based at leastin part on the one or more parameters. The apparatus also includes amemory coupled to the at least one processor.

In yet another aspect, an apparatus for utilizing PDN connectivity in awireless network is provided that includes means for obtaining one ormore parameters specifying whether PDN connectivity to a local gatewayis allowed at one or more access points and means for receiving arequest to establish a PDN connection to the local gateway whileconnected to at least one of the one or more access points. Theapparatus further includes means for determining whether to initiate thePDN connection to the local gateway at the at least one of the one ormore access points based at least in part on the one or more parameters.

Still, in another aspect, a computer-program product for utilizing PDNconnectivity in a wireless network is provided including acomputer-readable medium having code for causing at least one computerto obtain one or more parameters specifying whether PDN connectivity toa local gateway is allowed at one or more access points and code forcausing the at least one computer to receive a request to establish aPDN connection to the local gateway while connected to at least one ofthe one or more access points. The computer-readable medium furtherincludes code for causing the at least one computer to determine whetherto initiate the PDN connection to the local gateway using the at leastone of the one or more access points based at least in part on the oneor more parameters.

Moreover, in an aspect, an apparatus for utilizing PDN connectivity in awireless network is provided that includes a parameter receivingcomponent for obtaining one or more parameters specifying whether PDNconnectivity to a local gateway is allowed at one or more access pointsand a PDN request determining component for receiving a request toestablish a PDN connection to the local gateway while connected to atleast one of the one or more access points. The apparatus furtherincludes a PDN connection requesting component for determining whetherto initiate the PDN connection to the local gateway at the at least oneof the one or more access points based at least in part on the one ormore parameters.

According to another example, a method for utilizing PDN connectivity inwireless networks is provided including receiving a request from adevice to establish a PDN connection with an access point specifying anAPN and determining the APN relates to PDN connectivity to a localgateway. The method further includes determining the device is notallowed to establish the PDN connection at the access point based ondetermining the APN relates to PDN connectivity to the local gateway andsending one or more PDN connectivity parameters to the device indicatingone or more access points with which the device is not able to establishPDN connections to the local gateway for the APN.

In another aspect, an apparatus for utilizing PDN connectivity in awireless network is provided. The apparatus includes at least oneprocessor configured to receive a request from a device to establish aPDN connection with an access point specifying an access point name(APN) and determine the APN relates to PDN connectivity to a localgateway. The at least one processor can be further configured todetermine the device is not allowed to establish the PDN connection atthe access point based at least in part on determining the APN relatesto PDN connectivity to the local gateway and send one or more PDNconnectivity parameters to the device indicating one or more accesspoints with which the device is not able to establish PDN connections tothe local gateway for the APN. The apparatus also includes a memorycoupled to the at least one processor.

In yet another aspect, an apparatus for utilizing PDN connectivity in awireless network is provided that includes means for receiving a requestfrom a device to establish a PDN connection with an access pointspecifying an APN and means for determining the device is not allowed toestablish the PDN connection to a local gateway at the access pointbased at least in part on determining the APN relates to PDNconnectivity to the local gateway. The apparatus further includes meansfor sending one or more PDN connectivity parameters to the deviceindicating one or more access points with which the device is not ableto establish PDN connections to the local gateway for the APN.

Still, in another aspect, a computer-program product for utilizing PDNconnectivity in a wireless network is provided including acomputer-readable medium having code for causing at least one computerto receive a request from a device to establish a PDN connection with anaccess point specifying an APN and code for causing the at least onecomputer to determine the APN relates to PDN connectivity to a localgateway. The computer-readable medium further includes code for causingthe at least one computer to determine the device is not allowed toestablish the PDN connection at the access point based at least in parton determining the APN relates to PDN connectivity to the local gatewayand code for causing the at least one computer to send one or more PDNconnectivity parameters to the device indicating one or more accesspoints with which the device is not able to establish PDN connections tothe local gateway for the APN.

Moreover, in an aspect, an apparatus for utilizing PDN connectivity in awireless network is provided that includes a PDN connection requestreceiving component for receiving a request from a device to establish aPDN connection with an access point specifying an APN and a PDNconnectivity determining component for determining the device is notallowed to establish the PDN connection to a local gateway at the accesspoint based at least in part on determining the APN relates to PDNconnectivity to the local gateway. The apparatus further includes a PDNconnectivity indicating component for sending one or more PDNconnectivity parameters to the device indicating one or more accesspoints with which the device is not able to establish PDN connections tothe local gateway for the APN.

According to yet another example, a method for establishing a PDNconnection is provided herein. The method includes determining toestablish a PDN connection to a local gateway while communicating withan access point and selecting an APN that corresponds to PDNconnectivity to the local gateway at the access point. The methodfurther includes transmitting a request to establish a PDN connection tothe access point specifying the APN.

In another aspect, an apparatus for establishing a PDN connection isprovided. The apparatus includes at least one processor configured todetermine to establish a PDN connection to a local gateway whilecommunicating with an access point and select an APN that corresponds toPDN connectivity to the local gateway at the access point. The at leastone processor can be further configured to transmit a request toestablish the PDN connection to the access point specifying the APN. Theapparatus also includes a memory coupled to the at least one processor.

In yet another aspect, an apparatus for establishing a PDN connection isprovided that includes means for determining to establish a PDNconnection to a local gateway while communicating with an access point.The apparatus further includes means for transmitting a request toestablish the PDN connection to the access point specifying an APN thatcorresponds to PDN connectivity to the local gateway at the accesspoint.

Still, in another aspect, a computer-program product for establishing aPDN connection is provided including a computer-readable medium havingcode for causing at least one computer to determine to establish a PDNconnection to a local gateway while communicating with an access pointand code for causing the at least one computer to select an APN thatcorresponds to PDN connectivity to the local gateway at the accesspoint. The computer-readable medium further includes code for causingthe at least one computer to transmit a request to establish the PDNconnection to the access point specifying the APN.

Moreover, in an aspect, an apparatus for establishing a PDN connectionis provided that includes a PDN request determining component fordetermining to establish a PDN connection to a local gateway whilecommunicating with an access point. The apparatus further includes a PDNconnection requesting component for transmitting a request to establishthe PDN connection to the access point specifying an APN thatcorresponds to PDN connectivity to the local gateway at the accesspoint.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements, andin which:

FIG. 1 is a block diagram of an aspect of an example system forcommunicating packet data network (PDN) connectivity parameters.

FIG. 2 is a block diagram of an aspect of an example system fordetermining whether to establish a PDN connection to one or more accesspoints.

FIG. 3 is a flow chart of an aspect of an example methodology fordetermining whether to establish a PDN connection.

FIG. 4 is a flow chart of an aspect of an example methodology thatcommunicates PDN connectivity parameters.

FIG. 5 is a flow chart of an aspect of an example methodology fortransmitting a PDN connection request.

FIG. 6 is a block diagram of an example mobile device for determiningwhether to establish a PDN connection.

FIG. 7 is a block diagram of an example computing device according tovarious aspects described herein.

FIG. 8 is a block diagram of an example system that determines whetherto establish a PDN connection.

FIG. 9 is a block diagram of an example system that communicates PDNconnectivity parameters.

FIG. 10 is a block diagram of an example system that transmits a PDNconnection request.

FIG. 11 is a block diagram of an example wireless communication systemin accordance with various aspects set forth herein.

FIG. 12 is an illustration of an example wireless network environmentthat can be employed in conjunction with the various systems and methodsdescribed herein.

FIG. 13 illustrates an example wireless communication system, configuredto support a number of devices, in which the aspects herein can beimplemented.

FIG. 14 is an illustration of an exemplary communication system toenable deployment of femtocells within a network environment.

FIG. 15 illustrates an example of a coverage map having several definedtracking areas.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

As described further herein, packet data network (PDN) connectivity canbe managed for one or more devices. For example, a device can determinewhether to request or initiate PDN connectivity with a gateway from anaccess point based at least in part on one or more parameters receivedfrom one or more mobile network components. For example, the one or moreparameters can specify whether PDN connectivity is allowed at one ormore access points or groups of access points (e.g., a closed subscribergroup) for the device, whether one or more access point names (APN)allow PDN connectivity, and/or the like. The device can receive the oneor more parameters in subscription information, closed subscriber group(CSG) subscription information, etc., from one or more core mobilenetwork nodes, as part of a rejected PDN connection attempt, and/or thelike. Thus, the device can accordingly determine whether to request orinitiate a PDN connection using a given access point and/or using aspecific APN to prevent unnecessary signaling in situations where a PDNconnection from the device would otherwise be rejected.

As used in this application, the terms “component,” “module,” “system”and the like are intended to include a computer-related entity, such asbut not limited to hardware, firmware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a computing device and the computing device can be a component. Oneor more components can reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets, such as data from one component interactingwith another component in a local system, distributed system, and/oracross a network such as the Internet with other systems by way of thesignal.

Furthermore, various aspects are described herein in connection with aterminal, which can be a wired terminal or a wireless terminal. Aterminal can also be called a system, device, subscriber unit,subscriber station, mobile station, mobile, mobile device, remotestation, remote terminal, access terminal, user terminal, terminal,communication device, user agent, user device, or user equipment (UE). Awireless terminal may be a cellular telephone, a satellite phone, acordless telephone, a Session Initiation Protocol (SIP) phone, awireless local loop (WLL) station, a personal digital assistant (PDA), ahandheld device having wireless connection capability, a computingdevice, or other processing devices connected to a wireless modem.Moreover, various aspects are described herein in connection with a basestation. A base station may be utilized for communicating with wirelessterminal(s) and may also be referred to as an access point, a Node B,evolved Node B (eNB), or some other terminology.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTEand GSM are described in documents from an organization named “3rdGeneration Partnership Project” (3GPP). Additionally, cdma2000 and UMBare described in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). Further, such wireless communicationsystems may additionally include peer-to-peer (e.g., mobile-to-mobile)ad hoc network systems often using unpaired unlicensed spectrums, 802.xxwireless LAN, BLUETOOTH and any other short- or long-range, wirelesscommunication techniques.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches may also be used.

Referring to FIG. 1, illustrated are several nodes of a samplecommunication system 100. For illustration purposes, various aspects ofthe disclosure are described in the context of one or more devices,access points, and network nodes that communicate with one another. Itis to be appreciated, however, that aspects herein may be applicable toother types of apparatuses or other similar apparatuses that arereferenced using other terminology. For example, access points can bereferred to or implemented as base stations, eNodeBs (eNB), Home Node Bs(e.g., in UMTS) or Home eNBs (e.g., in LTE), collectively referred to asH(e)NBs, femtocell or picocell access points, mobile base stations,relay nodes, hot-spots, routers, gateways, etc., while devices may bereferred to or implemented as user equipment (UE), mobile devices,access terminals, modems (or other tethered devices), or may be aportion thereof, and so on.

Device 102 can receive one or more services (e.g., network connectivity)from access point 104. Device 102 can be a wired or wireless deviceinstalled within and/or traveling throughout a coverage area provided byaccess point 104 and/or one or more access points of the system 100. Forexample, at various points in time, device 102 can connect to an accesspoint 104 or some other access point in the system 100 (not shown) overa wired or wireless interface. Each of these access points cancommunicate with one or more network nodes (represented, for example, bynetwork node(s) 106) to facilitate wide area network connectivity.Network nodes 106 can include one or more radio and/or core networknodes in a mobile network, for example. Thus, in various examples,network nodes 106 can represent functionality such as at least one of:network management (e.g., via an operation, administration, management(OAM), and/or provisioning entity), call control, session management,mobility management, subscription management, gateway functions,interworking functions, or some other suitable network functionality.Network nodes 106 can include a mobility manager 108, which can be amobility management entity (MME), serving general packet radio services(GPRS) support node (SGSN), mobile switching center (MSC), visitorlocation register (VLR), etc., a subscription server 110, which can be ahome subscriber server (HSS), home location register (HLR), etc., and/orthe like, that can be part of a one or more PLMNs accessible by device102.

In some cases, device 102 can access a restricted group access point(e.g., access point 104) associated with a wireless cell set. Ingeneral, a wireless cell set comprises a set of one or more cells (e.g.,provided by at least one access point, such as access point 104) havinga defined relationship. An example of a wireless cell set is a CSG. Forconvenience, the discussion that follows may simply refer to the termCSG, rather than the more general term wireless cell set. It should beappreciated, however, that the described concepts may be applicable toother types of defined sets or groups (e.g., restricted groups) ofwireless cells or other similar entities. Also, restricted groups canprovide a diminished level of access to non-members (which can bereferred to as hybrid-mode access, or the cells within the group ashybrid cells), to which aspects described herein can apply as well. Inaddition, it is to be appreciated that an access point, such as accesspoint 104, can provide one or more cells within which devices cancommunicate with the access point.

As depicted, access point 104 can be coupled to a router 112 or otherdevice to access Internet 114, and access point 104 can allow device 102to communicate with network nodes 106 via Internet 114. In anotherexample, access point 104 can connect to Internet 114 using a directbroadband connection (e.g., via a modem). Moreover, for example, accesspoint 104 can be coupled to a gateway 116, which can be a local gatewaythat allows communication between one or more local network devices 118and 120, and access point 104, allows access to router 112, etc. Thoughshown as co-located with access point 104 in the depicted example, it isto be appreciated that gateway 116 can be implemented within accesspoint 104, as a separate entity from access point 104, and/or the like.Moreover, for example, router 112 can be similarly co-located withaccess point 104 and/or gateway 116, implemented within access point104, and/or the like. In any case, access point 104 can receivecommunications from device 102 intended for nodes in a mobile networkand can forward the communications to network nodes 106 through router112 and via Internet 114 to provide mobile network access to device 102.For example, the communications can be associated with one or morecommunications tunnels, and access point 104 can determine that thepackets are intended for one or more of network nodes 106 based on theone or more communications tunnels (e.g., based on one or moreparameters, such as a tunnel identifier, destination address, etc., inpacket headers).

For example, to facilitate communicating between device 102 and gateway116, a radio bearer can be established between access point 104 anddevice 102. For example, a first mobile network bearer between gateway116 and another component of the mobile network, such as one or more ofnetwork node(s) 106, can be established, as well as a second mobilenetwork bearer between access point 104 and the other component of themobile network (e.g., before, after, and/or as part of establishing theradio bearer). Thus, in one example, communications related to device102 intended for gateway 116 can traverse the other component of themobile network (e.g., via router 112 and Internet 114) from access point104 to arrive at gateway 116.

In addition, in one example, access point 104 may provide PDNconnectivity to facilitate at least one of decreasing load on thenetwork nodes 106, providing access to local network resources, and/orthe like. For example, the access point 104 may provide local internetprotocol (IP) access (LIPA), selected IP traffic offload (SIPTO), etc.,to one or more devices for allowing access to local IP components,offloading traffic from the one or more devices to a connection toInternet 114, etc. without traversing network nodes 106. Where accesspoint 104 provides PDN connectivity, for example, device 102 can accessrouter 112, local network device 118 and/or 120, etc. using a localgateway 116 directly without traversing any of network node(s) 106. Inthis example, device 102 can initiate a PDN connection to access point104, which can initially be received by mobility manager 108 to ensuredevice 102 is allowed to initiate the PDN connection. Where device 102is permitted to initiate PDN connectivity with access point 104, a PDNbearer or other communication tunnel can be established between accesspoint 104 and gateway 116 for allowing device 102 communications withone or more nodes, such as router 112, local network devices 118 and/or120, etc. In one example, data received over the radio bearer betweendevice 102 and access point 104 can be sent over the PDN bearer betweenaccess point 104 and gateway 116, and similarly, communications intendedfor device 102 can be received from router 112, local network devices118 and/or 120, etc., and gateway 116 can forward the communications tothe device 102 via the PDN bearer with access point 104.

For example, gateway 116 additionally communicates with local networkdevices 118 and 120 to provide sharing of resources therebetween, accessto Internet 114 via router 112, and/or the like. For example, localnetwork devices 118 and 120 can be substantially any device operable tocommunicate in a network, such as a local area network (LAN) or wirelessLAN (WLAN) device (e.g., a computer, server, printer, digital videorecorder (DVR), mobile device, a portion thereof, or substantially anydevice with a processor (or access to a processor) and a networkinterface, etc.), and/or the like. Moreover, since access point 104 iscoupled with gateway 116, for example, access point 104 participates inthe local network with local network devices 118 and 120, and can thusaccess resources or services offered by local network devices 118 and/or120 in the local network, and/or can allow access to resources relatedto access point 104 or provide services thereto. In another example,local network devices 118 and 120 can be connected to router 112, whichcan similarly provide access thereto.

In this regard, gateway 116 can provide PDN connectivity in the form ofLIPA where the access point 104 can establish LIPA bearers with gateway116 for device 102. In this example, devices, such as device 102, canperform actions such as at least one of accessing the services orresources of the local network, providing local network devices with 118and 120 with services or access to resources of the device via accesspoint 104, and/or the like through gateway 116 via access point 104without traversing network node 106 or similar nodes of the mobilenetwork. Gateway 116 can also provide PDN connectivity in the form ofSIPTO, as described, by offloading communications from device 102 viaaccess point 104 to router 112.

For example, access point 104 may or may not allow PDN connectivity todevice 102 or to any devices, and/or may provide PDN connectivity forcertain APNs. As described further herein, device 102 can receive PDNconnectivity parameters 122 that specify whether device 102 can initiatea PDN connection to a gateway 116 from access point 104, from one ormore CSGs that may include access point 104, from one or more networks(e.g., public land mobile networks (PLMN)) that may include access point104, and/or using one or more APNs that can be used for initiating thePDN connection. For example, device 102 can receive the PDN connectivityparameters 122 as part of subscription information and/or CSGsubscription information (e.g., from subscription server 110), uponinitiating a PDN connection with access point 104 (e.g., from mobilitymanager 108), and/or the like. If the PDN connectivity parameters 122indicate that device 102 cannot initiate a PDN connection through accesspoint 104, using a certain APN or otherwise, device 102 can refrain fromrequesting the PDN connection, which can mitigate unnecessary signaling.

Additionally, device 102 can determine an alternative action wheredevice 102 is unable to request the PDN connection from access point104. Moreover, for example, device 102 can receive PDN connectionparameters from mobility manager 108 as part of a rejected PDNconnection attempt to access point 104, as described further herein.These PDN connectivity parameters, for example, can specify a CSG orPLMN for which device 102 cannot request PDN connections (e.g., relatingto certain APNs or otherwise). Moreover, though described in terms ofestablishing PDN connections (e.g., in LTE networks), it is to beappreciated that aspects described herein can be similarly applied toestablishing packet data protocol (PDP) contexts (e.g., in UMTSnetworks).

Turning to FIG. 2, an example wireless communication system 200 isillustrated that facilitates determining whether to initiate PDNconnections in a wireless network. System 200 can include a device 202that can communicate with one or more access points to receive access toa mobile network, an access point 104 that provides open or restrictedaccess or a combination thereof to one or more devices, and a gateway116 that facilitates communicating with one or more networks. System 200also comprises a router 112 that can facilitate communications betweenaccess point 104 or gateway 116 and an Internet 114, as described, aswell as a network device 118 that can be coupled to gateway 116.Moreover, system 200 comprises a subscription server 204 that providessubscription information related to a device, and a mobility manager 206that authenticates one or more devices to communicate with one or morecore network components.

In one example, device 202 can be a UE, modem (or other tethereddevice), a portion thereof, and/or the like, and access point 104 can bea femtocell, picocell, H(e)NB, or similar access point, a portionthereof, etc., as described. In addition, for example, gateway 116 canbe a substantially any gateway or router, such as but not limited to aserving gateway (S-GW) packet data network (PDN) gateway (P-GW), agateway GPRS support node (GGSN), etc., and mobility manager 206 can bea MME, SGSN, MSC, VLR, or similar node. In addition, as described,gateway 116 can be co-located and/or implemented within access point 104in another example. Subscription server 204 can be an HSS, HLR, orsimilar component. Moreover, it is to be appreciated that additionalcomponents or nodes can be present between those shown (e.g., one ormore gateways or routers can be present between access point 104 andgateway 116, between access point 104 and mobility manager 206, betweenmobility manager 206 and subscription server 204, etc.) to facilitateaccess.

As described, in one example, access point 104 can provide PDNconnectivity to device 202 in the form of LIPA with gateway 116 forcommunicating with network device 118 through gateway 116, in the formof SIPTO with gateway 116 for offloading packets to router 112 forcommunicating over Internet 114, etc., without traversing corecomponents of a mobile network, such as mobility manager 206 (e.g.,other than for authentication of device 202 in initially establishingthe PDN connection). In one example, as described above however, accesspoint 104 may not allow PDN connections, may allow PDN connections forcertain APNs, etc. for a given device.

Device 202 can comprise a parameter receiving component 208 forobtaining PDN connectivity parameters from one or more core componentsof a mobile network, a PDN request determining component 210 forobtaining a request for initiating a PDN connection, and a PDNconnection requesting component 212 for determining whether to initiatea PDN connection with the access point based at least in part on the PDNconnectivity parameters. Subscription server 204 can comprise asubscription data component 214 for communicating subscriptioninformation to a device. Mobility manager 206 can optionally include aPDN connection request receiving component 216 for obtaining a PDNconnection request from a device, a PDN connectivity determiningcomponent 218 for determining whether the device is permitted toestablish a PDN connection with an access point, and/or a PDNconnectivity indicating component 220 for communicating PDN connectivityparameters to the device based at least in part on the PDN connectionrequest.

According to an example, device 202 can communicate with access point104 to receive access to a mobile network, as described. In an example,upon requesting mobile network access from access point 104, accesspoint 104 can communicate with one or more core network componentsthrough router 112 and Internet 114, such as mobility manager 206 and/orsubscription server 204. For example, mobility manager 206 can beutilized to authenticate device 202 to communicate in the mobilenetwork. In addition, subscription data component 214 can retrievesubscription information corresponding to the device 202 forcommunicating thereto. The subscription information can be generalsubscription information for device 202, CSG subscription informationrelating to CSGs of which device 202 is a member, and/or the like. Inaddition, for example, subscription data component 214 can communicatePDN connectivity parameters 222 as part of device 202 subscriptioninformation or CSG subscription information. For example, subscriptionserver 204 can communicate the PDN connectivity parameters 222—e.g.,along with or as part of the subscription information—to device 202 viaconnection with access point 104 (e.g., through Internet 114, router112, etc).

As described, the PDN connectivity parameters 222 can relate to whethercertain access points, a set of access points (e.g., access pointscorresponding to the same CSG, PLMN, etc.), and/or the like allow PDNconnections to a local gateway, for example gateway 116, APNs for whichPDN connections are allowed at the access points, CSGs, PLMNs, etc.,and/or the like, which can be specific for the device 202. As described,for example, gateway 116 can be a local gateway that allows access torouter 112, network device 118, etc., and/or to/from access point 104depending on one or more parameters, as described herein. Thus, forexample, the PDN connectivity parameters 222 can include a list ofaccess points (e.g., by identifier) from which device 202 can initiate aPDN connection (e.g., a LIPA and/or SIPTO PDN connection) to a localgateway. In another example, the PDN connectivity parameters 222 caninclude a list of CSGs (e.g., by identifier) with which device 202 caninitiate a PDN connection. In yet another example, the PDN connectivityparameters 222 can include a list of APNs for each access point or CSGin the list for which device can initiate a PDN connection.

In another example, the PDN connectivity parameters 222 can be anextension of a list, such as one or more parameters in a list thatspecify whether the device 202 is able to initiate a PDN connection fora given list item. Thus, for example, the PDN connectivity parameters222 can include an indicator for one or more CSGs listed in CSGsubscription information specifying whether PDN connections to a localgateway are allowed for the CSG and/or which type of PDN connections areallowed (e.g., LIPA, SIPTO, etc.). In another example, thus, the PDNconnectivity parameters 222 can be a list of APNs relating to each CSGlisted in the CSG subscription information for which PDN connections (orcertain types of PDN connections) are allowed, and/or the like. Again,the list of APNs can be a list of all APNs with indicators for thoseAPNs for which PDN connections are allowed, a list of those APNs forwhich PDN connections are allowed, and/or the like.

In any case, parameter receiving component 208 can obtain the PDNconnectivity parameters 222 for determining whether to request a PDNconnection in one or more instances. In another example, parameterreceiving component 208 can obtain the PDN connectivity parameters 222from one or more other core mobile network components (e.g., as part ofan open mobile alliance (OMA) device management (DM) procedure thatincludes the PDN connectivity parameters for one or more correspondingaccess points, CSGs, etc., and/or the like). For example, PDN requestdetermining component 210 can obtain a request for a PDN connection fromwithin device 202, a system utilizing device 202 (e.g., a computer wheredevice 202 is a modem), and/or the like. In this example, PDN connectionrequesting component 212 can determine whether to initiate a PDNconnection from an access point, determine an APN to utilize forrequesting the PDN connection from the access point, and/or the likebased at least in part on the PDN connectivity parameters 222.

For example, device 202 can be communicating with access point 104,which can include an active mode connection to access point 104 foraccessing the mobile network, an idle-mode connection to access point104 for receiving paging signals from the mobile network, and/or thelike. Upon PDN request determining component 210 obtaining a request forPDN connectivity to a local gateway, PDN connection requesting component212 can determine whether to request PDN connectivity to the localgateway (e.g., gateway 116) from access point 104 based on the PDNconnectivity parameters 222. For example, where the PDN connectivityparameters 222 specify that access point 104 does not allow PDNconnections to a local gateway, PDN connection requesting component 212can refrain from requesting a PDN connection. In this example, device202 can take an alternative action, such as requesting a PDN connectionfrom one or more neighboring access points (not shown) if permitted.Where PDN connectivity parameters 222 specify that access point 104 doesallow PDN connections to a local gateway, PDN connection requestingcomponent 212 can initiate a PDN connection with access point 104 bytransmitting a PDN connectivity request (e.g., a LIPA PDN connectivityrequest, SIPTO PDN connectivity request, etc.) thereto, as described.

In a more specific example, PDN connection requesting component 212 candetermine whether the device 202 is allowed to request a PDN connectionto a local gateway from access points of a CSG or PLMN related to accesspoint 104. For example, device 202 can receive an indication of the CSGor PLMN of access point 104 by virtue of communicating therewith, andPDN connection requesting component 212 can determine whether PDNconnectivity parameters 222 specify that a PDN connection (e.g., or acertain type of PDN connection, such as LIPA, SIPTO, etc.) is allowedfor the CSG or PLMN. PDN connection requesting component 212 canaccordingly initiate or refrain from initiating a PDN connection togateway 116 via access point 104.

In yet another example, PDN request determining component 210 can obtaina APN related to the requested PDN connection. PDN connection requestingcomponent 212 can accordingly determine whether a PDN connection isallowed for the APN at access point 104, at the corresponding CSG orPLMN, etc., based at least in part on the PDN connectivity parameters222. PDN connection requesting component 212 can accordingly initiate orrefrain from initiating the PDN connection.

In another example, based on PDN request determining component 210obtaining a request for a PDN connection to a local gateway, PDNconnection requesting component 212 can select an APN for specifying inrequesting a PDN connection with access point 104. For example, PDNconnection requesting component 212 can determine one or more APNs forwhich PDN connections (e.g., and/or certain types of PDN connections)are allowed at access point 104. For example, this can include PDNconnection requesting component 212 determining the one or more APNsspecified in the PDN connectivity parameters 222 relating to allowingPDN connectivity for device 202 at access point 104, at a CSG of whichaccess point 104 is a member, at a PLMN of access point 104, and/or thelike. PDN connection requesting component 212 can accordingly select theAPN based at least in part on the request for the PDN connection (e.g.,and/or a type of PDN connection specified in the request for the PDNconnection) to specify in requesting the PDN connection.

Moreover, in an example, the PDN connectivity parameters 222 can specifydiffering levels of PDN connectivity, and PDN connection requestingcomponent 212 can further determine whether to initiate a PDN connectionto the local gateway, such as gateway 116, from access point 104 basedon the levels of PDN connectivity. For example, where the PDNconnectivity parameters 222 correspond to LIPA, an indication of whetherLIPA is allowed via access point 104 can correspond to levels ofallowance, such as LIPA only, LIPA conditional, or LIPA prohibited. Forexample, a level of allowance can be associated with one or more APNsrelated to access point 104, a CSG of access point 104, a PLMN of accesspoint 104, etc., in the PDN connectivity parameters 222. In thisexample, PDN connection requesting component 212 can refrain fromestablishing a PDN connection for a related APN (e.g., received at PDNrequest determining component 210) using access point 104 where LIPAprohibited is specified for the APN. In another example, where LIPAconditional is specified, PDN connection requesting component 212 canrefrain from establishing the PDN connection using access point 104where the respective condition is not met. In one example, the conditioncan relate to a location of device 202, a network within which thedevice 202 is communicating (e.g., a network related to gateway 116) ora related address, and/or the like.

Furthermore, for example, where PDN request determining component 210obtains a request for a PDN connection without an APN specified, PDNconnection requesting component 212 can select a PDN in the PDNconnectivity parameters 222 for which LIPA only is specified (e.g., orLIPA conditional so long as the condition is specified) for requestingthe PDN connectivity, if such an APN exists in the PDN connectivityparameters 222.

In another example, PDN connection requesting component 212 can attemptto initiate a PDN connection to access point 104 where access point 104may not allow such connections from device 202. For example, the device202 may not have been provisioned with PDN connectivity parameters 222,incorrectly provisioned, etc. In another example, the PDN connectivityparameters 222 can be removed from device 202 (e.g., by PDN connectionrequesting component 212 or another component) based at least in part onexpiration of a timer, powering down device 202, removal of a subscriberidentity modulate (SIM) card from the device 202, based on device 202communicating with one or more other access points, and/or other eventsor triggers. In any case, access point 104 can communicate with mobilitymanager 206 on behalf of device 202 to authenticate the device 202 forthe PDN connection. For example, PDN connection request receivingcomponent 216 can obtain the PDN connection request of device 202 fromaccess point 104.

In this example, PDN connectivity determining component 218, forexample, can determine the request is for PDN connectivity (e.g., basedon the APN specified in the request). For example, PDN connectivitydetermining component 218 can determine the APN in the request is a PDNconnectivity APN based at least in part on information received foraccess point 104. Thus, PDN connectivity determining component 218 canalso determine whether device 202 is permitted to initiate PDNconnections to a local gateway at the access point 104. This can bebased at least in part on PDN connectivity parameters 224 received fordevice 202 (e.g., during device 202 initialization on the mobilenetwork), PDN connectivity parameters 224 can be received from accesspoint 104 or an access point management server, an indication fromaccess point 104 that device 202 is not allowed to request PDNconnectivity from access point 104, and/or the like. For example, thePDN connectivity parameters 224 can be different from PDN connectivityparameters 222, as described below, while still indicating informationrelated to whether device 202 can request PDN connectivity with certainaccess points, CSGs, PLMNs, etc.

In any case, where PDN connectivity determining component 218 determinesthat device 202 is not allowed to initiate a PDN connection to a localgateway, such as gateway 116, using access point 104, PDN connectivityindicating component 220 can specify PDN connectivity parameters 224 todevice 202 along with an indication that device 202 is unable toinitiate a PDN connection using access point 104. PDN connectivityparameters 224, for example, can specify that device 202 is notpermitted to initiate a PDN connection using access point 104, using anyaccess points in the same CSG as access point 104, using any accesspoints in the same PLMN as access point 104, and/or the like. Forexample, the PDN connectivity parameters 224 can include a specific CSGand/or PLMN identifier and an indication that device 202 cannot initiatePDN connections from access points advertising or otherwise related tothe CSG or PLMN identifier.

In one example, PDN connectivity indicating component 220 cancommunicate the PDN connectivity parameters 224 to device using one ormore non-access stratum (NAS) messages. In an example, the PDNconnectivity parameters 224 can correspond to a cause code in the one ormore NAS messages for rejecting the PDN connectivity request from device202. In one example, PDN connection requesting component 212 can obtainthe cause code and can determine the PDN connectivity parameters 224.For example, the cause code can indicate that device 202 is unable toestablish PDN connections to a local gateway using any access point inthe CSG or PLMN of access point 104. In this example, PDN connectionrequesting component 212 can store a CSG and/or PLMN identifier relatedto access point 104 for subsequently comparing to one or more otheraccess points in determining whether to attempt PDN connection using theone or more other access points. Parameter receiving component 208 canobtain the PDN connectivity parameters 224, and PDN connectionrequesting component 212 can utilize the PDN connectivity parameters 224in subsequently determining whether to initiate a PDN connection usingone or more other access points, as described above with respect to PDNconnectivity parameters 222.

For example, when communicating with another access point (not shown),PDN connection requesting component 212 can determine whether the otheraccess points are in the same CSG or part of the same PLMN as accesspoint 104; if so, PDN connection requesting component 212 can refrainfrom initiating a PDN connection thereto based at least in part on thePDN connectivity parameters 224 indicating PDN connections are notallowed in the CSG or PLMN. In one example, PDN connectivity parameters224 can be or can be similar to or a subset of PDN connectivityparameters 222 as related to device 202, access point 104, one or moreCSGs or PLMNs, etc. Furthermore, device 202 can remove PDN connectivityparameters 224 based at least in part on one or more events or triggers,as described in connection with PDN connectivity parameters 222.

Referring to FIGS. 3-5, example methodologies relating to determiningwhether to initiate PDN connections in a wireless network areillustrated. While, for purposes of simplicity of explanation, themethodologies are shown and described as a series of acts, it is to beunderstood and appreciated that the methodologies are not limited by theorder of acts, as some acts may, in accordance with one or moreembodiments, occur in different orders and/or concurrently with otheracts from that shown and described herein. For example, it is to beappreciated that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with one or more embodiments.

Referring to FIG. 3, an example methodology 300 is displayed thatfacilitates determining whether to initiate a PDN connection to anaccess point. At 302, one or more parameters can be received specifyingwhether PDN connectivity to a local gateway is allowed at one or moreaccess points. For example, the one or more parameters can correspond toPDN connectivity parameters received in subscription information, CSGsubscription information, etc., received from a network component aspart of a NAS message rejecting a request for a PDN connection using anaccess point, and/or the like. In addition, the one or more parameterscan correspond to indicators specifying whether PDN connections areallowed at an access point, at access points related to a CSG, at accesspoints related to a PLMN, etc., and can be device-specific. Moreover,the one or more parameters can indicate a level of PDN connectivity to alocal gateway (e.g., LIPA only, LIPA conditional, LIPA prohibited,etc.).

At 304, a request to establish a PDN connection to the local gateway canbe received while connected to at least one of the one or more accesspoints. In an example, the request can specify an APN to utilize inestablishing the PDN connection at the at least one access point. Inanother example, an APN can be selected based at least in part ondetermining the request is for a PDN connection (e.g., based ondetermining one or more APNs in the one or more parameters that specifyPDN connections are allowed for the APN). At 306, it can be determinedwhether to initiate the PDN connection to the local gateway using the atleast one of the one or more access points based at least in part on theone or more parameters. For example, this can include determiningwhether PDN connections are allowed (e.g., to the access point, to a CSGrelated to the access point, to a PLMN related to the access point, fora specified APN, etc.) based on the one or more parameters, anddetermining to initiate the PDN connection where allowed, as described.In another example, where not allowed, it can be determined not toinitiate the PDN connection at 306. Where the one or more parameters donot specify whether PDN connections are allowed for the access points,CSG, PLMN, related to the APN, etc., a PDN connection can be attempted,in one example, and if not allowed, PDN connection parameters can bereceived with a rejection, as described. In another example, where theone or more parameters do not specify whether PDN connections areallowed, it can be determined not to initiate the PDN connection at 306.

Turning to FIG. 4, an example methodology 400 is displayed thatfacilitates rejecting a PDN connection request from a device. At 402, arequest can be received from a device specifying an APN to establish aPDN connection with an access point. At 404, it can be determined thatthe APN relates to PDN connectivity at a local gateway. For example,this can be based at least in part on one or more PDN connectivityparameters related to the device or access point received from one ormore core network components, the access point, and/or the like. Asdescribed, the one or more PDN connectivity parameters can correspond toa list of APNs for which PDN connectivity is allowed, which cancorrespond to an access point, a list of access points, CSGs, PLMNs,etc., for which the device can request a PDN connection, and/or thelike.

At 406, it can be determined that the device is not allowed to establishthe PDN connection at the access point based on determining the APNrelates to PDN connectivity to the local gateway. Thus, as described,this can be based at least in part on the PDN connection parametersspecifying that the device is not allowed PDN connections for the APN,at the access point, CSG, or PLMN, etc., and/or the PDN connectionparameters not specifying that the device can request PDN connectionsfor the APN, at the access point, CSG, PLMN, etc. At 408, one or morePDN connectivity parameters can be sent to the device indicating one ormore access points with which the device is not able to establish PDNconnections to the local gateway for the APN. Thus, for example, the oneor more PDN connectivity parameters can specify one or more accesspoints related to the access point, a CSG of the access point, a PLMN ofthe access point, etc., for which the device cannot establish PDNconnections (e.g., for the APN or otherwise). For example, this can bepart of one or more cause codes in a NAS rejection message rejectingestablishment of the PDN connection. As described, the concepts can beapplied for PDP contexts as well, and thus where the above stepscorrespond to a PDN connection, it is to be appreciated that the stepscan be modified for PDP contexts.

Referring to FIG. 5, an example methodology 500 for communicating arequest to establish a PDN connection is illustrated. At 502, it can bedetermined to establish a PDN connection to a local gateway whilecommunicating with an access point. For example, a request can bereceived for establishing the PDN connection (e.g., from an application,a device, etc.). At 504, an APN that corresponds to PDN connectivity tothe local gateway at the access point can be selected. For example, thiscan include determining an APN from the PDN connectivity parameters forwhich PDN connectivity is allowed. At 506, a request to establish a PDNconnection specifying the APN can be transmitted to the access point. Inone example, the PDN connection can be established with the localgateway via the access point.

It will be appreciated that, in accordance with one or more aspectsdescribed herein, inferences can be made regarding determining whetherto request to establish a PDN connection based on PDN connectivityparameters, determining an APN to specify for requesting a PDNconnection, and/or the like, as described. As used herein, the term to“infer” or “inference” refers generally to the process of reasoningabout or inferring states of the system, environment, and/or user from aset of observations as captured via events and/or data. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states, for example. The inference can beprobabilistic—that is, the computation of a probability distributionover states of interest based on a consideration of data and events.Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether or not the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources.

FIG. 6 is an illustration of a mobile device 600 that facilitatesdetermining whether to initiate a PDN connection. Mobile device 600comprises a receiver 602 that receives a signal from, for instance, areceive antenna (not shown), performs typical actions on (e.g., filters,amplifies, downconverts, etc.) the received signal, and digitizes theconditioned signal to obtain samples. Receiver 602 can comprise ademodulator 604 that can demodulate received symbols and provide them toa processor 606 for channel estimation. Processor 606 can be a processordedicated to analyzing information received by receiver 602 and/orgenerating information for transmission by a transmitter 608, aprocessor that controls one or more components of mobile device 600,and/or a processor that both analyzes information received by receiver602, generates information for transmission by transmitter 608, andcontrols one or more components of mobile device 600. For example,processor 606 can perform one or more functions as described herein todetermine whether to request a PDN connection.

Mobile device 600 can additionally comprise memory 610 that isoperatively coupled to processor 606 and that can store data to betransmitted, received data, information related to available channels,data associated with analyzed signal and/or interference strength,information related to an assigned channel, power, rate, or the like,and any other suitable information for estimating a channel andcommunicating via the channel. Memory 610 can additionally storeprotocols and/or algorithms associated with estimating and/or utilizinga channel (e.g., performance based, capacity based, etc.), determiningwhether to request a PDN connection, and/or the like.

It will be appreciated that the data store (e.g., memory 610) describedherein can be either volatile memory or nonvolatile memory, or caninclude both volatile and nonvolatile memory. By way of illustration,and not limitation, nonvolatile memory can include read only memory(ROM), programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable PROM (EEPROM), or flash memory. Volatile memorycan include random access memory (RAM), which acts as external cachememory. By way of illustration and not limitation, RAM is available inmany forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).The memory 610 of the subject systems and methods is intended tocomprise, without being limited to, these and any other suitable typesof memory.

Processor 606 can further be optionally operatively coupled to aparameter receiving component 612, which can be similar to parameterreceiving component 208, a PDN request determining component 614, whichcan be similar to PDN request determining component 210, and/or a PDNconnection requesting component 616, which can be similar to PDNconnection requesting component 212. Mobile device 600 still furthercomprises a modulator 618 that modulates signals for transmission bytransmitter 608 to, for instance, a base station, another mobile device,etc. Although depicted as being separate from the processor 606, it isto be appreciated that the parameter receiving component 612, PDNrequest determining component 614, PDN connection requesting component616, demodulator 604, and/or modulator 618 can be part of the processor606 or multiple processors (not shown), and/or stored as instructions inmemory 610 for execution by processor 606.

Referring to FIG. 7, in one aspect, any of network nodes 106, mobilitymanagers 108, or 206, subscription servers 110 or 204, etc. (e.g., FIGS.1-2) can be represented by computer device 700. Computer device 700includes a processor 702 for carrying out processing functionsassociated with one or more of components and functions describedherein. Processor 702 can include a single or multiple set of processorsor multi-core processors. Moreover, processor 702 can be implemented asan integrated processing system and/or a distributed processing system.

Computer device 700 further includes a memory 704, such as for storinglocal versions of applications being executed by processor 702. Memory704 can include substantially any type of memory usable by a computer,such as random access memory (RAM), read only memory (ROM), tapes,magnetic discs, optical discs, volatile memory, non-volatile memory, andany combination thereof. Computer device 700 also includes one or morecomponents 706-718, which can be stored in memory 704, executed byprocessor 702 (e.g., based on instructions stored in memory 704), beimplemented within one or more processors 702, and/or the like.

Further, computer device 700 includes a communications component 706that provides for establishing and maintaining communications with oneor more parties utilizing hardware, software, and services as describedherein. Communications component 706 may carry communications betweencomponents on computer device 700, as well as between computer device700 and external devices, such as devices located across acommunications network and/or devices serially or locally connected tocomputer device 700. For example, communications component 706 mayinclude one or more buses, and may further include transmit chaincomponents and receive chain components associated with a transmitterand receiver, respectively, operable for interfacing with externaldevices.

Additionally, computer device 700 may further include a data store 708,which can be any suitable combination of hardware and/or software, thatprovides for mass storage of information, databases, and programsemployed in connection with aspects described herein. For example, datastore 708 may be a data repository for applications not currently beingexecuted by processor 702.

Computer device 700 may optionally include an interface component 710operable to receive inputs from a user of computer device 700, andfurther operable to generate outputs for presentation to the user.Interface component 710 may include one or more input devices, includingbut not limited to a keyboard, a number pad, a mouse, a touch-sensitivedisplay, a navigation key, a function key, a microphone, a voicerecognition component, any other mechanism capable of receiving an inputfrom a user, or any combination thereof. Further, interface component710 may include one or more output devices, including but not limited toa display, a speaker, a haptic feedback mechanism, a printer, any othermechanism capable of presenting an output to a user, or any combinationthereof. In another example, interface component 710 can be anapplication programming interface (API) that can be accessed by one ormore devices to perform functions on computer device 700.

In addition, in the depicted example, computer device 700 can optionallyinclude one or more of subscription data component 712, which can besimilar to subscription data component 214, PDN connection requestreceiving component 714, which can be similar to PDN connection requestreceiving component 216, PDN connectivity determining component 716,which can be similar to PDN connectivity determining component 218,and/or PDN connectivity indicating component 718, which can be similarto PDN connectivity indicating component 220. Thus, these components712, 714, 716, and/or 718 can utilize processor 702 to executeinstructions associated therewith, memory 704 to store informationassociated therewith, communications component 706 to carry outcommunications, and/or the like, as described. In addition, it is to beappreciated that computer device 700 can include additional oralternative components described herein.

With reference to FIG. 8, illustrated is a system 800 that determineswhether to initiate a PDN connection with an access point. For example,system 800 can reside at least partially within a device, etc. It is tobe appreciated that system 800 is represented as including functionalblocks, which can be functional blocks that represent functionsimplemented by a processor, software, or combination thereof (e.g.,firmware). System 800 includes a logical grouping 802 of electricalcomponents that can act in conjunction. For instance, logical grouping802 can include an electrical component for obtaining one or moreparameters specifying whether PDN connectivity to a local gateway isallowed at one or more access points 804. As described, the one or moreparameters can be PDN connectivity parameters received from one or morenetwork components, an access point, and/or the like, as described.

Further, logical grouping 802 can comprise an electrical component forreceiving a request to establish a PDN connection to the local gatewaywhile connected to at least one of the one or more access points 806.For example, this can include receiving a request from an application,another device using system 800, and/or the like. Additionally, therequest can include an APN that corresponds to PDN connectivity, asdescribed above. Moreover, logical grouping 802 can include anelectrical component for determining whether to initiate the PDNconnection to the local gateway at the at least one of the one or moreaccess points based at least in part on the one or more parameters 808.Thus, for example, electrical component 808 can determine such based atleast in part on the APN in the request, one or more PDN connectivityparameters corresponding to the at least one access point, a CSG or PLMNthereof, etc.

For example, electrical component 804 can include a parameter receivingcomponent 208, as described above. In addition, for example, electricalcomponent 806, in an aspect, can include a PDN request determiningcomponent 210, as described above. Moreover, electrical component 808can include a PDN connection requesting component 212, as described.Additionally, system 800 can include a memory 810 that retainsinstructions for executing functions associated with the electricalcomponents 804, 806, and 808. While shown as being external to memory810, it is to be understood that one or more of the electricalcomponents 804, 806, and 808 can exist within memory 810.

In one example, electrical components 804, 806, and 808 can comprise atleast one processor, or each electrical component 804, 806, and 808 canbe a corresponding module of at least one processor. Moreover, in anadditional or alternative example, electrical components 804, 806, and808 can be a computer program product comprising a computer readablemedium, where each electrical component 804, 806, and 808 can becorresponding code.

With reference to FIG. 9, illustrated is a system 900 that sends PDNconnectivity parameters to a device for which a PDN connection requestis rejected. For example, system 900 can reside at least partiallywithin an MME, SGSN, etc. It is to be appreciated that system 900 isrepresented as including functional blocks, which can be functionalblocks that represent functions implemented by a processor, software, orcombination thereof (e.g., firmware). System 900 includes a logicalgrouping 902 of electrical components that can act in conjunction. Forinstance, logical grouping 902 can include an electrical component forreceiving a request from a device to establish a PDN connection with anaccess point specifying an APN 904. For example, the device can selectthe APN for requesting a PDN connection. Further, logical grouping 902can comprise an electrical component for determining the device is notallowed to establish the PDN connection to a local gateway at the accesspoint based at least in part on determining the APN relates to PDNconnectivity 906.

For example, the APN can correspond to PDN connectivity, however,electrical component 906 can determine that the device is not allowedPDN connections with the access point based at least in part on one ormore PDN connectivity parameters related to the access point, a CSG orPLMN thereof, etc. In addition, as described, the PDN connectivityparameters can be specific for the device and/or the specified APN.Moreover, logical grouping 902 can include an electrical component forsending one or more PDN connectivity parameters to the device indicatingone or more access points with which the device is not allowed toestablish PDN connections to the local gateway for the APN 908. Forexample, the PDN connectivity parameters can specify a CSG, PLMN, one ormore access point identifiers, APNs, etc., for which the device is notallowed to request PDN connection. As described, the device can then usethe PDN connectivity parameters in determining whether to subsequentlyrequest PDN connections with other access points in the CSG, PLMN, etc.

For example, electrical component 904 can include a PDN connectionrequest receiving component 216, as described above. In addition, forexample, electrical component 906, in an aspect, can include a PDNconnectivity determining component 218, as described above. Moreover,electrical component 908 can include a PDN connectivity indicatingcomponent 220, as described. Additionally, system 900 can include amemory 910 that retains instructions for executing functions associatedwith the electrical components 904, 906, and 908. While shown as beingexternal to memory 910, it is to be understood that one or more of theelectrical components 904, 906, and 908 can exist within memory 910.

In one example, electrical components 904, 906, and 908 can comprise atleast one processor, or each electrical component 904, 906, and 908 canbe a corresponding module of at least one processor. Moreover, in anadditional or alternative example, electrical components 904, 906, and908 can be a computer program product comprising a computer readablemedium, where each electrical component 904, 906, and 908 can becorresponding code.

With reference to FIG. 10, illustrated is a system 1000 thatcommunicates a request to establish a PDN connection. For example,system 1000 can reside at least partially within a device, etc. It is tobe appreciated that system 1000 is represented as including functionalblocks, which can be functional blocks that represent functionsimplemented by a processor, software, or combination thereof (e.g.,firmware). System 1000 includes a logical grouping 1002 of electricalcomponents that can act in conjunction. For instance, logical grouping1002 can include an electrical component for determining to establish aPDN connection to a local gateway while communicating with an accesspoint 1004. For example, this can be determined based on a request froman application or device communicating with system 1000, etc.

Further, logical grouping 1002 can comprise an electrical component fortransmitting a request to establish a PDN connection to the access pointspecifying an APN that corresponds to the PDN connectivity to the localgateway at the access point 1006. As described, for example, the APN canbe determined from PDN connectivity parameters that indicate the APN canbe used to establish PDN connections with the access point. For example,electrical component 1004 can include a PDN request determiningcomponent 210, as described above. In addition, for example, electricalcomponent 1006, in an aspect, can include a PDN connection requestingcomponent 212, as described above. Additionally, system 1000 can includea memory 1008 that retains instructions for executing functionsassociated with the electrical components 1004 and 1006. While shown asbeing external to memory 1008, it is to be understood that one or moreof the electrical components 1004 and 1006 can exist within memory 1008.

In one example, electrical components 1004 and 1006 can comprise atleast one processor, or each electrical component 1004 and 1006 can be acorresponding module of at least one processor. Moreover, in anadditional or alternative example, electrical components 1004 and 1006can be a computer program product comprising a computer readable medium,where each electrical component 1004 and 1006 can be corresponding code.

Referring now to FIG. 11, a wireless communication system 1100 isillustrated in accordance with various embodiments presented herein.System 1100 comprises a base station 1102 that can include multipleantenna groups. For example, one antenna group can include antennas 1104and 1106, another group can comprise antennas 1108 and 1110, and anadditional group can include antennas 1112 and 1114. Two antennas areillustrated for each antenna group; however, more or fewer antennas canbe utilized for each group. Base station 1102 can additionally include atransmitter chain and a receiver chain, each of which can in turncomprise a plurality of components associated with signal transmissionand reception (e.g., processors, modulators, multiplexers, demodulators,demultiplexers, antennas, etc.), as is appreciated.

Base station 1102 can communicate with one or more mobile devices suchas mobile device 1116 and mobile device 1122; however, it is to beappreciated that base station 1102 can communicate with substantiallyany number of mobile devices similar to mobile devices 1116 and 1122.Mobile devices 1116 and 1122 can be, for example, cellular phones, smartphones, laptops, handheld communication devices, handheld computingdevices, satellite radios, global positioning systems, PDAs, and/or anyother suitable device for communicating over wireless communicationsystem 1100. As depicted, mobile device 1116 is in communication withantennas 1112 and 1114, where antennas 1112 and 1114 transmitinformation to mobile device 1116 over a forward link 1118 and receiveinformation from mobile device 1116 over a reverse link 1120. Moreover,mobile device 1122 is in communication with antennas 1104 and 1106,where antennas 1104 and 1106 transmit information to mobile device 1122over a forward link 1124 and receive information from mobile device 1122over a reverse link 1126. In a frequency division duplex (FDD) system,forward link 1118 can utilize a different frequency band than that usedby reverse link 1120, and forward link 1124 can employ a differentfrequency band than that employed by reverse link 1126, for example.Further, in a time division duplex (TDD) system, forward link 1118 andreverse link 1120 can utilize a common frequency band and forward link1124 and reverse link 1126 can utilize a common frequency band.

Each group of antennas and/or the area in which they are designated tocommunicate can be referred to as a sector of base station 1102. Forexample, antenna groups can be designed to communicate to mobile devicesin a sector of the areas covered by base station 1102. In communicationover forward links 1118 and 1124, the transmitting antennas of basestation 1102 can utilize beamforming to improve signal-to-noise ratio offorward links 1118 and 1124 for mobile devices 1116 and 1122. Also,while base station 1102 utilizes beamforming to transmit to mobiledevices 1116 and 1122 scattered randomly through an associated coverage,mobile devices in neighboring cells can be subject to less interferenceas compared to a base station transmitting through a single antenna toall its mobile devices. Moreover, mobile devices 1116 and 1122 cancommunicate directly with one another using a peer-to-peer or ad hoctechnology as depicted. According to an example, system 1100 can be amultiple-input multiple-output (MIMO) communication system.

FIG. 12 shows an example wireless communication system 1200. Thewireless communication system 1200 depicts one base station 1210 and onemobile device 1250 for sake of brevity. However, it is to be appreciatedthat system 1200 can include more than one base station and/or more thanone mobile device, wherein additional base stations and/or mobiledevices can be substantially similar or different from example basestation 1210 and mobile device 1250 described below. In addition, it isto be appreciated that base station 1210 and/or mobile device 1250 canemploy the systems (FIGS. 1, 2, and 8-11), methods (FIGS. 3-5), mobiledevices (FIG. 6), and/or computer devices, (FIG. 7) described herein tofacilitate wireless communication there between. For example, componentsor functions of the systems and/or methods described herein can be partof a memory 1232 and/or 1272 or processors 1230 and/or 1270 describedbelow, and/or can be executed by processors 1230 and/or 1270 to performthe disclosed functions.

At base station 1210, traffic data for a number of data streams isprovided from a data source 1212 to a transmit (TX) data processor 1214.According to an example, each data stream can be transmitted over arespective antenna. TX data processor 1214 formats, codes, andinterleaves the traffic data stream based on a particular coding schemeselected for that data stream to provide coded data.

The coded data for each data stream can be multiplexed with pilot datausing orthogonal frequency division multiplexing (OFDM) techniques.Additionally or alternatively, the pilot symbols can be frequencydivision multiplexed (FDM), time division multiplexed (TDM), or codedivision multiplexed (CDM). The pilot data is typically a known datapattern that is processed in a known manner and can be used at mobiledevice 1250 to estimate channel response. The multiplexed pilot andcoded data for each data stream can be modulated (e.g., symbol mapped)based on a particular modulation scheme (e.g., binary phase-shift keying(BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying(M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected forthat data stream to provide modulation symbols. The data rate, coding,and modulation for each data stream can be determined by instructionsperformed or provided by processor 1230.

The modulation symbols for the data streams can be provided to a TX MIMOprocessor 1220, which can further process the modulation symbols (e.g.,for OFDM). TX MIMO processor 1220 then provides N_(T) modulation symbolstreams to N_(T) transmitters (TMTR) 1222 a through 1222 t. In variousembodiments, TX MIMO processor 1220 applies beamforming weights to thesymbols of the data streams and to the antenna from which the symbol isbeing transmitted.

Each transmitter 1222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel.Further, N_(T) modulated signals from transmitters 1222 a through 1222 tare transmitted from N_(T) antennas 1224 a through 1224 t, respectively.

At mobile device 1250, the transmitted modulated signals are received byN_(R) antennas 1252 a through 1252 r and the received signal from eachantenna 1252 is provided to a respective receiver (RCVR) 1254 a through1254 r. Each receiver 1254 conditions (e.g., filters, amplifies, anddownconverts) a respective signal, digitizes the conditioned signal toprovide samples, and further processes the samples to provide acorresponding “received” symbol stream.

An RX data processor 1260 can receive and process the N_(R) receivedsymbol streams from N_(R) receivers 1254 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. RX dataprocessor 1260 can demodulate, deinterleave, and decode each detectedsymbol stream to recover the traffic data for the data stream. Theprocessing by RX data processor 1260 is complementary to that performedby TX MIMO processor 1220 and TX data processor 1214 at base station1210.

The reverse link message can comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message can be processed by a TX data processor 1238, whichalso receives traffic data for a number of data streams from a datasource 1236, modulated by a modulator 1280, conditioned by transmitters1254 a through 1254 r, and transmitted back to base station 1210.

At base station 1210, the modulated signals from mobile device 1250 arereceived by antennas 1224, conditioned by receivers 1222, demodulated bya demodulator 1240, and processed by a RX data processor 1242 to extractthe reverse link message transmitted by mobile device 1250. Further,processor 1230 can process the extracted message to determine whichprecoding matrix to use for determining the beamforming weights.

Processors 1230 and 1270 can direct (e.g., control, coordinate, manage,etc.) operation at base station 1210 and mobile device 1250,respectively. Respective processors 1230 and 1270 can be associated withmemory 1232 and 1272 that store program codes and data. Processors 1230and 1270 can also perform computations to derive frequency and impulseresponse estimates for the uplink and downlink, respectively.

FIG. 13 illustrates a wireless communication system 1300, configured tosupport a number of users, in which the teachings herein may beimplemented. The system 1300 provides communication for multiple cells1302, such as, for example, macro cells 1302A-1302G, with each cellbeing serviced by a corresponding access node 1304 (e.g., access nodes1304A-1304G). As shown in FIG. 13, access terminals 1306 (e.g., accessterminals 1306A-1306L) can be dispersed at various locations throughoutthe system over time. Each access terminal 1306 can communicate with oneor more access nodes 1304 on a forward link (FL) and/or a reverse link(RL) at a given moment, depending upon whether the access terminal 1306is active and whether it is in soft handoff, for example. The wirelesscommunication system 1300 can provide service over a large geographicregion.

FIG. 14 illustrates an exemplary communication system 1400 where one ormore femto nodes are deployed within a network environment.Specifically, the system 1400 includes multiple femto nodes 1410A and1410B (e.g., femtocell nodes or H(e)NB) installed in a relatively smallscale network environment (e.g., in one or more user residences 1430).Each femto node 1410 can be coupled to a wide area network 1440 (e.g.,the Internet) and a mobile operator core network 1450 via a digitalsubscriber line (DSL) router, a cable modem, a wireless link, or otherconnectivity means (not shown). As will be discussed below, each femtonode 1410 can be configured to serve associated access terminals 1420(e.g., access terminal 1420A) and, optionally, alien access terminals1420 (e.g., access terminal 1420B). In other words, access to femtonodes 1410 can be restricted such that a given access terminal 1420 canbe served by a set of designated (e.g., home) femto node(s) 1410 but maynot be served by any non-designated femto nodes 1410 (e.g., a neighbor'sfemto node).

FIG. 15 illustrates an example of a coverage map 1500 where severaltracking areas 1502 (or routing areas or location areas) are defined,each of which includes several macro coverage areas 1504. Here, areas ofcoverage associated with tracking areas 1502A, 1502B, and 1502C aredelineated by the wide lines and the macro coverage areas 1504 arerepresented by the hexagons. The tracking areas 1502 also include femtocoverage areas 1506. In this example, each of the femto coverage areas1506 (e.g., femto coverage area 1506C) is depicted within a macrocoverage area 1504 (e.g., macro coverage area 1504B). It should beappreciated, however, that a femto coverage area 1506 may not lieentirely within a macro coverage area 1504. In practice, a large numberof femto coverage areas 1506 can be defined with a given tracking area1502 or macro coverage area 1504. Also, one or more pico coverage areas(not shown) can be defined within a given tracking area 1502 or macrocoverage area 1504.

Referring again to FIG. 14, the owner of a femto node 1410 can subscribeto mobile service, such as, for example, 3G mobile service, offeredthrough the mobile operator core network 1450. In addition, an accessterminal 1420 can be capable of operating both in macro environments andin smaller scale (e.g., residential) network environments. Thus, forexample, depending on the current location of the access terminal 1420,the access terminal 1420 can be served by an access node 1460 or by anyone of a set of femto nodes 1410 (e.g., the femto nodes 1410A and 1410Bthat reside within a corresponding user residence 1430). For example,when a subscriber is outside his home, he is served by a standard macrocell access node (e.g., node 1460) and when the subscriber is at home,he is served by a femto node (e.g., node 1410A). Here, it should beappreciated that a femto node 1410 can be backward compatible withexisting access terminals 1420.

A femto node 1410 can be deployed on a single frequency or, in thealternative, on multiple frequencies. Depending on the particularconfiguration, the single frequency or one or more of the multiplefrequencies can overlap with one or more frequencies used by a macrocell access node (e.g., node 1460). In some aspects, an access terminal1420 can be configured to connect to a preferred femto node (e.g., thehome femto node of the access terminal 1420) whenever such connectivityis possible. For example, whenever the access terminal 1420 is withinthe user's residence 1430, it can communicate with the home femto node1410.

In some aspects, if the access terminal 1420 operates within the mobileoperator core network 1450 but is not residing on its most preferrednetwork (e.g., as defined in a preferred roaming list), the accessterminal 1420 can continue to search for the most preferred network(e.g., femto node 1410) using a Better System Reselection (BSR), whichcan involve a periodic scanning of available systems to determinewhether better systems are currently available, and subsequent effortsto associate with such preferred systems. Using an acquisition tableentry (e.g., in a preferred roaming list), in one example, the accessterminal 1420 can limit the search for specific band and channel. Forexample, the search for the most preferred system can be repeatedperiodically. Upon discovery of a preferred femto node, such as femtonode 1410, the access terminal 1420 selects the femto node 1410 forcamping within its coverage area.

A femto node can be restricted in some aspects. For example, a givenfemto node can only provide certain services to certain accessterminals. In deployments with so-called restricted (or closed)association, a given access terminal can only be served by the macrocell mobile network and a defined set of femto nodes (e.g., the femtonodes 1410 that reside within the corresponding user residence 1430). Insome implementations, a femto node can be restricted to not provide, forat least one access terminal, at least one of: signaling, data access,registration, paging, or service.

In some aspects, a restricted femto node (which can also be referred toas a Closed Subscriber Group H(e)NB) is one that provides service to arestricted provisioned set of access terminals. This set can betemporarily or permanently extended as necessary. In some aspects, aClosed Subscriber Group (CSG) can be defined as the set of access nodes(e.g., femto nodes) that share a common access control list of accessterminals. A channel on which all femto nodes (or all restricted femtonodes) in a region operate can be referred to as a femto channel.

Various relationships can thus exist between a given femto node and agiven access terminal. For example, from the perspective of an accessterminal, an open femto node can refer to a femto node with norestricted association. A restricted femto node can refer to a femtonode that is restricted in some manner (e.g., restricted for associationand/or registration). A home femto node can refer to a femto node onwhich the access terminal is authorized to access and operate on. Aguest femto node can refer to a femto node on which an access terminalis temporarily authorized to access or operate on. An alien femto nodecan refer to a femto node on which the access terminal is not authorizedto access or operate on, except for perhaps emergency situations (e.g.,911 calls).

From a restricted femto node perspective, a home access terminal canrefer to an access terminal that authorized to access the restrictedfemto node. A guest access terminal can refer to an access terminal withtemporary access to the restricted femto node. An alien access terminalcan refer to an access terminal that does not have permission to accessthe restricted femto node, except for perhaps emergency situations, forexample, 911 calls (e.g., an access terminal that does not have thecredentials or permission to register with the restricted femto node).

For convenience, the disclosure herein describes various functionalityin the context of a femto node. It should be appreciated, however, thata pico node can provide the same or similar functionality as a femtonode, but for a larger coverage area. For example, a pico node can berestricted, a home pico node can be defined for a given access terminal,and so on.

A wireless multiple-access communication system can simultaneouslysupport communication for multiple wireless access terminals. Asmentioned above, each terminal can communicate with one or more basestations via transmissions on the forward and reverse links. The forwardlink (or downlink) refers to the communication link from the basestations to the terminals, and the reverse link (or uplink) refers tothe communication link from the terminals to the base stations. Thiscommunication link can be established via a single-in-single-out system,a MIMO system, or some other type of system.

The various illustrative logics, logical blocks, modules, components,and circuits described in connection with the embodiments disclosedherein may be implemented or performed with a general purpose processor,a digital signal processor (DSP), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may comprise one or more modules operable to perform one ormore of the steps and/or actions described above. An exemplary storagemedium may be coupled to the processor, such that the processor can readinformation from, and write information to, the storage medium. In thealternative, the storage medium may be integral to the processor.Further, in some aspects, the processor and the storage medium mayreside in an ASIC. Additionally, the ASIC may reside in a user terminal.In the alternative, the processor and the storage medium may reside asdiscrete components in a user terminal.

In one or more aspects, the functions, methods, or algorithms describedmay be implemented in hardware, software, firmware, or any combinationthereof. If implemented in software, the functions may be stored ortransmitted as one or more instructions or code on a computer-readablemedium, which may be incorporated into a computer program product.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable media that can be accessed by a computer. By way of example,and not limitation, such computer-readable media can comprise RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tocarry or store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, substantiallyany connection may be termed a computer-readable medium. For example, ifsoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs usually reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/orembodiments, it should be noted that various changes and modificationscould be made herein without departing from the scope of the describedaspects and/or embodiments as defined by the appended claims.Furthermore, although elements of the described aspects and/orembodiments may be described or claimed in the singular, the plural iscontemplated unless limitation to the singular is explicitly stated.Additionally, all or a portion of any aspect and/or embodiment may beutilized with all or a portion of any other aspect and/or embodiment,unless stated otherwise.

What is claimed is:
 1. A method for utilizing packet data network (PDN)connectivity in a wireless network, comprising: receiving, at a userequipment (UE), one or more parameters specifying whether PDNconnectivity to a local gateway is allowed for the UE at one or moreaccess points, wherein the one or more parameters are based onsubscription information specific to the UE, wherein the subscriptioninformation is from a home network of the UE, and wherein the one ormore parameters comprise a list of access point names (APNs) indicatingthe one or more access points for which PDN connectivity is allowed atthe local gateway; and determining, at the UE, whether to initiate a PDNconnection to the local gateway from at least one of the one or moreaccess points based at least in part on the one or more parameters,wherein the UE determines to initiate the PDN connection if an APN ofthe at least one of the one or more access points is included in thelist of APNs.
 2. The method of claim 1, wherein the determining whetherto initiate the PDN connection comprises determining based on a locationof the UE.
 3. The method of claim 1, wherein determining whether toinitiate the PDN connection comprises determining while connected to atleast one of the one or more access points.
 4. The method of claim 1,further comprising receiving a request to establish the PDN connectionto the local gateway, wherein the determining whether to initiate thePDN connection comprises determining in response to receiving therequest.
 5. The method of claim 1, further comprising transmitting a PDNconnectivity request for the PDN connection at the local gateway toanother one of the one or more access points, wherein the receiving theone or more parameters is in response to the PDN connectivity request.6. The method of claim 1, wherein the one or more parameters comprise anindication that PDN connectivity to the local gateway is not allowed ata set of access points.
 7. The method of claim 6, wherein the set ofaccess points comprise the at least one of the one or more access pointsand another one of the one or more access points, and the determiningincludes determining not to initiate the PDN connection.
 8. The methodof claim 1, wherein the one or more access points comprise access pointscorresponding to access points in a same closed subscriber group.
 9. Themethod of claim 1, wherein the one or more access points comprise accesspoints corresponding to access points in a same public land mobilenetwork.
 10. The method of claim 1, wherein the PDN connectioncorresponds to a local Internet Protocol (IP) access (LIPA) PDNconnection or a selected IP traffic offload (SIPTO) connection, and thePDN connectivity to the local gateway corresponds to a LIPA PDNconnectivity or a SIPTO PDN connectivity.
 11. The method of claim 1,wherein the receiving the one or more parameters comprises receiving theone or more parameters as part of an open mobile alliance devicemanagement procedure.
 12. The method of claim 1, further comprisingremoving the one or more parameters based at least in part on one ormore triggers or events.
 13. An apparatus for utilizing packet datanetwork (PDN) connectivity in a wireless network, comprising: at leastone processor configured to: receive, at a user equipment (UE), one ormore parameters specifying whether PDN connectivity to a local gatewayis allowed for the UE at one or more access points, wherein the one ormore parameters are based on subscription information specific to theUE, wherein the subscription information is from a home network of theUE, and wherein the one or more parameters comprise a list of accesspoint names (APNs) indicating the one or more access points for whichPDN connectivity is allowed at the local gateway; and determine, at theUE, whether to initiate a PDN connection to the local gateway from atleast one of the one or more access points based at least in part on theone or more parameters, wherein the determining comprises determining toinitiate the PDN connection if an APN of the at least one of the one ormore access points is included in the list of APNs.
 14. The apparatus ofclaim 13, wherein the at least one processor is configured to determinewhether to initiate the PDN connection by determining based on alocation of the UE.
 15. The apparatus of claim 13, wherein the at leastone processor is configured to determine whether to initiate the PDNconnection by determining whether to initiate the PDN connection whileconnected to at least one of the one or more access points.
 16. Theapparatus of claim 13, wherein the at least one processor is furtherconfigured to receive a request to establish the PDN connection to thelocal gateway, wherein the determining whether to initiate the PDNconnection comprises determining in response to receiving the request.17. The apparatus of claim 13, wherein the at least one processor isfurther configured to transmit a PDN connectivity request for the PDNconnection at the local gateway to another one of the one or more accesspoints, wherein the receiving the one or more parameters is in responseto the PDN connectivity request.
 18. The apparatus of claim 13, whereinthe one or more parameters comprise an indication that PDN connectivityto the local gateway is not allowed at a set of access points.
 19. Theapparatus of claim 18, wherein the set of access points comprises the atleast one of the one or more access points and the another one of theone or more access points, and the determining includes determining notto initiate the PDN connection.
 20. The apparatus of claim 13, whereinthe one or more access points comprises access points in a same closedsubscriber group.
 21. The apparatus of claim 13, wherein the one or moreaccess points comprises access points in a same public land mobilenetwork.
 22. The apparatus of claim 13, wherein the PDN connectioncorresponds to a local Internet Protocol (IP) access (LIPA) PDNconnection or a selected IP traffic offload (SIPTO) connection, and thePDN connectivity to the local gateway corresponds to a LIPA PDNconnectivity or a SIPTO PDN connectivity.
 23. The apparatus of claim 13,wherein the at least one processor is configured to receive the one ormore parameters by receiving the one or more parameters as part of anopen mobile alliance device management procedure.
 24. The apparatus ofclaim 13, wherein the at least one processor is configured to remove theone or more parameters based at least in part on one or more triggers orevents.
 25. An apparatus for utilizing packet data network (PDN)connectivity in a wireless network, comprising: means for receiving, ata user equipment (UE), one or more parameters specifying whether PDNconnectivity to a local gateway is allowed for the UE at one or moreaccess points, wherein the one or more parameters are based onsubscription information specific to the UE, wherein the subscriptioninformation is from a home network of the UE, and wherein the one ormore parameters comprise a list of access point names (APNs) indicatingthe one or more access points for which PDN connectivity is allowed atthe local gateway; and means for determining, at the UE, whether toinitiate a PDN connection to the local gateway from at least one of theone or more access points based at least in part on the one or moreparameters, wherein the UE determines to initiate the PDN connection ifan APN of the at least one of the one or more access points is includedin the list of APNs.
 26. The apparatus of claim 25, wherein the meansfor determining whether to initiate the PDN connection comprises meansfor determining based on a location of the UE.
 27. The apparatus ofclaim 25, wherein the means for determining whether to initiate the PDNconnection comprises means for determining while connected to at leastone of the one or more access points.
 28. The apparatus of claim 25,further comprising means for receiving a request to establish the PDNconnection to the local gateway, wherein the means for determiningwhether to initiate the PDN connection comprises means for determiningin response to receiving the request.
 29. A non-transitory computerreadable memory storing instructions which, when executed by one or moreprocessors, cause the one or more processors to: receive, at a userequipment (UE), one or more parameters specifying whether PDNconnectivity to a local gateway is allowed for the UE at one or moreaccess points, wherein the one or more parameters are based onsubscription information specific to the UE, wherein the subscriptioninformation is from a home network of the UE, and wherein the one ormore parameters comprise a list of access point names (APNs) indicatingthe one or more access points for which PDN connectivity is allowed atthe local gateway; and determine, at the UE, whether to initiate a PDNconnection to the local gateway from at least one of the one or moreaccess points based at least in part on the one or more parameters,wherein the determining comprises determining to initiate the PDNconnection if an APN of the at least one of the one or more accesspoints is included in the list of APNs.
 30. The computer readable memoryof claim 29, wherein the instructions cause the one or more processorsto determine whether to initiate the PDN connection by determining basedon a location of the UE.
 31. The computer readable memory of claim 29,wherein the instructions cause the one or more processors to determinewhether to initiate the PDN connection by determining whether toinitiate the PDN connection while connected to at least one of the oneor more access points.
 32. The computer readable memory of claim 29,wherein the instructions further cause the one or more processors toreceive a request to establish the PDN connection to the local gateway,wherein the determining whether to initiate the PDN connection comprisesdetermining in response to receiving the request.